-
-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added LunaSea Support #1072
Added LunaSea Support #1072
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #1072 +/- ##
========================================
Coverage 99.27% 99.28%
========================================
Files 136 137 +1
Lines 17753 17874 +121
Branches 3623 3649 +26
========================================
+ Hits 17625 17746 +121
Misses 119 119
Partials 9 9 ☔ View full report in Codecov by Sentry. |
0c6b0d8
to
46946a7
Compare
10ea34d
to
a26e9f2
Compare
̶G̶e̶t̶t̶i̶n̶g̶ ̶a̶n̶ ̶e̶r̶r̶o̶r̶ ̶w̶h̶e̶n̶ ̶t̶r̶y̶i̶n̶g̶ ̶t̶o̶ ̶u̶s̶e̶ ̶ Yup... was using wrong container for this repo.... |
Are you using my Docker container or LinuxServer.io? |
updated... was struggling getting Lunasea to work... finally figured it out... your container definitely works better |
LinuxServer.io is a great solution, but attachments are disabled out of the gate. I think i may need to still investigate why simple notifications aren't working with it in this state. |
Description:
Related issue (if applicable): #1070
Syntax
Valid syntax is as follows:
Cloud Hosting
lunasea://{toFireBaseUser}
lunasea://{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://+{toFireBaseDevice}
lunasea://+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
You can mix and match as well:
lunasea://{user}:{pass}@/+{toFireBaseUser1}/{toFireBaseDevice1}/
** Private Hosting**
This works the exact same way; you can just additionally specify your connection details to your local server:
lunasea://{user}:{pass}@{hostname}/{toFireBaseUser}
lunasea://{user}:{pass}@{hostname}/{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://{user}:{pass}@{hostname}/+{toFireBaseDevice}
lunasea://{user}:{pass}@{hostname}//+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
lunasea://{user}:{pass}@{hostname}:{port}/{toFireBaseUser}
lunasea://{user}:{pass}@{hostname}:{port}/{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://{user}:{pass}@{hostname}:{port}/+{toFireBaseDevice}
lunasea://{user}:{pass}@{hostname}:{port}//+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
You can mix and match as well:
lunasea://{user}:{pass}@{hostname}/+{toFireBaseUser1}/{toFireBaseDevice1}/
lunasea://{user}:{pass}@{hostname}:{port}/+{toFireBaseUser1}/{toFireBaseDevice1}/
Use
lunaseas://
for a Secure (https://
) connection andlunasea://
for Insecure (http://
).lsea://
andlseas://
can also be used as an alias tolunasee://
andlunaseas://
(respectively) if you choose.Parameter Breakdown
no
.cloud
andprivate
. This is detected if no otherwise specified. When set toprivate
, a hostname must be provided as part of the URL. When set tocloud
, all elements are presumed to be notification end points and https://lunasea.app is used. In cloud mode, all transactions are secure (regardless if you specifylunasea://
orlsea://
).New Service Completion Status
%global common_description
Checklist
flake8
)Testing
Anyone can help test this source code as follows: